Versioned Analytics Consent and Immediate Withdrawal - #1106

Summary

Prompts users to review analytics consent when the policy changes, and stops telemetry promptly when consent is withdrawn. Adds storage failure handling, tests, and consent documentation.

How was this tested?

• corepack pnpm exec vitest run --config vitest.config.js src/utils/__tests__/analyticsConsent.test.ts src/utils/__tests__/analytics.circuitBreaker.test.ts src/utils/__tests__/monitoring.consent.test.ts — 15 tests passed. Covers consent grant and withdrawal, stale policy re-prompting, malformed or unavailable storage, failed saves, queued event removal, active request cancellation, and observer shutdown.
• Ran a focused TypeScript check on the changed consent and monitoring files — passed.
• Ran ESLint on the changed files — passed with no errors; existing warnings remain.
• git diff --check — passed.
• The full repository test run did not complete and reported unrelated failures. Full type-check, lint, format, and build checks also have repository-level failures, so full CI is not verified as passing.

Merge requirements

A PR is merged only when every box below is true. See
Merge requirements for the full policy.

• All required CI checks pass on the latest commit (not just an earlier push).
• No required checks are failing, pending, or skipped — re-run or fix them; do not ask for a merge while any are outstanding.
• The branch has no merge conflicts with the target branch (rebase or merge master if GitHub shows "This branch has conflicts").
• Tests were added or updated for the change (primary flow, a boundary case, and a failure case).
• Docs were updated where behaviour, configuration, or security posture changed.

Closes #834